ci: make the bundled DKMS module list a matrix field - #89
ci: make the bundled DKMS module list a matrix field#89Christopher Obbard (obbardc) wants to merge 1 commit into
Conversation
|
On keying it by distro family: Third thing, for whatever consumes |
The set of out-of-tree DKMS modules bundled into the kernel image is currently fixed by the packaging branch alone so it cannot differ per kernel variant, delivery or suite. Add a "dkms" field to every matrix row, keyed by suite, carrying "kgsl" on all suites as per the existing packaging. A flat list could not express what qcom-next Daily needs: it expands trixie, forky and resolute from one row. A suite with no key builds no out-of-tree modules. resolve-matrix.sh validates each list (module names without the -dkms suffix, no commas, no duplicates) and rejects a key naming a suite its row does not build, so a stale or typo'd key cannot sit there looking effective. Because the resolver already flattens one entry per suite, it picks each leg's own list there and joins it into a comma-separated string, exactly as it already does for kernel_config; nothing downstream needs to know the field is keyed. daily.yml and release.yml thread the result through as the new dkms input of build-kernel-deb.yml, which passes it to prepare-source.sh as --dkms when non-empty. Signed-off-by: Christopher Obbard <chris.obbard@oss.qualcomm.com>
41a9744 to
43617f9
Compare
|
Description still says a list field carrying kgsl for all variants as per the existing packaging, but it's an object keyed by suite now and Worth a second look at the "kgsl has no resolute build" line too. From the latest daily, resolute leg: and in the resulting packages: camx and iris are the ones that don't build on Ubuntu, as you said on #84.
|
2 participants
The set of out-of-tree DKMS modules bundled into the kernel image is currently fixed by the packaging branch alone so it cannot differ per kernel variant or delivery.
Add a list "dkms" field to every matrix row, carrying "kgsl" for all variants today as per the existing packaging. resolve-matrix.sh validates it (module names without the -dkms suffix, no commas, no duplicates) and joins it into a comma-separated string, exactly as it already does for kernel_config. daily.yml and release.yml thread it through as the new dkms input of build-kernel-deb.yml, which passes it to prepare-source.sh as --dkms when non-empty.
This is the sister-PR of #90; both are needed to land at the same time.